| Package | hl7.ehrs.uv.phrsfmr2 |
| Type | Requirements |
| Id | Id |
| FHIR Version | R5 |
| Source | http://hl7.org/ehrs/uv/phrsfmr2/https://build.fhir.org/ig/HL7/phrsfm-ig/Requirements-PHRSFMR2-PH.3.5.2.html |
| Url | http://hl7.org/ehrs/uv/phrsfmr2/Requirements/PHRSFMR2-PH.3.5.2 |
| Version | 2.0.1-ballot |
| Status | active |
| Date | 2025-04-03T15:15:30+00:00 |
| Name | PH_3_5_2_Manage_Tasks |
| Title | PH.3.5.2 Manage Tasks (Function) |
| Experimental | False |
| Authority | hl7 |
| Description | Healthcare events or activities that require the PHR Account Holder's participation can be organized as tasks. |
| Purpose | Care plans and other health care activities can be broken down into specific steps or tasks and organized on a task list that may be sorted by priority, date and time, problem, provider, and so forth. The task list entries should serve as an index to their supporting documents. Example(s): Directions for a dressing change at a specific time of day can be displayed as an entry on the task list. |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
Healthcare events or activities that require the PHR Account Holder's participation can be organized as tasks.
Care plans and other health care activities can be broken down into specific steps or tasks and organized on a task list that may be sorted by priority, date and time, problem, provider, and so forth. The task list entries should serve as an index to their supporting documents.
Example(s): Directions for a dressing change at a specific time of day can be displayed as an entry on the task list.
| PH.3.5.2#01 | SHOULD |
The system SHOULD provide the ability for the PHR Account Holder to manage self-care, health maintenance, preventive, and wellness tasks, including the management of task status (e.g., performed, rescheduled, or canceled). |
| PH.3.5.2#02 | SHOULD |
The system SHOULD provide the ability to determine a set of tasks for the PHR Account Holder based on a previously-defined set of business rules. |
| PH.3.5.2#03 | SHOULD |
The system SHOULD provide the ability to capture, maintain, and render an indication of the status of tasks (e.g., completed or performed). For example, the dressing for a laceration needs to be changed every three days, but the PHR Account Holder failed to note yesterday that the dressing was successfully changed as required. Another example is the requirement to post an indication to the PHR system regarding daily compliance with dietary guidelines. |
| PH.3.5.2#04 | dependent SHOULD |
The system SHOULD provide the ability to render tasks in a sorted manner (e.g., by status or priority) according to user-preference, organizational policy, and/or jurisdictional law. |
| PH.3.5.2#05 | SHOULD |
The system SHOULD present each task with a brief description and date on a task list included on the PHR Account Holder's summary view or dashboard. |
| PH.3.5.2#06 | SHOULD |
The system SHOULD provide the ability for the PHR Account Holder to capture, maintain, and render descriptions of health-related tasks (and associated dates/times for those tasks). |
| PH.3.5.2#07 | SHOULD |
The system SHOULD provide the ability to capture, maintain, and render communications that were received from others who are performing tasks (e.g., an indication from a member of a care team who completed or performed a certain task). |
| PH.3.5.2#08 | SHOULD |
The system SHOULD conform to TI.7 (Workflow Management) to manage workflows and tasks that involve communications with others. |
FHIR{
"resourceType" : "Requirements",
"id" : "PHRSFMR2-PH.3.5.2",
"meta" : {
"profile" : [
"http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/FMFunction"
]
},
"text" : {
"status" : "extensions",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <span id=\"description\"><b>Statement <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b> <div><p>Healthcare events or activities that require the PHR Account Holder's participation can be organized as tasks.</p>\n</div></span>\n\n \n <span id=\"purpose\"><b>Description <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Informative Content\" class=\"informative-flag\">I</a>:</b> <div><p>Care plans and other health care activities can be broken down into specific steps or tasks and organized on a task list that may be sorted by priority, date and time, problem, provider, and so forth. The task list entries should serve as an index to their supporting documents.</p>\n<p>Example(s): Directions for a dressing change at a specific time of day can be displayed as an entry on the task list.</p>\n</div></span>\n \n\n \n <span id=\"actors\"><b>Actors:</b><br/> ehr</span>\n \n\n \n <span id=\"requirements\"><b>Criteria <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b></span>\n \n <table id=\"statements\" class=\"grid dict\">\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.3.5.2#01</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability for the PHR Account Holder to manage self-care, health maintenance, preventive, and wellness tasks, including the management of task status (e.g., performed, rescheduled, or canceled).</p>\n</div></span>\n \n \n Satisfied by:<ol>\n \n <li><a href=\"https://www.hl7.org/fhir/task.html\">https://www.hl7.org/fhir/task.html</a></li>\n \n </ol>\n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.3.5.2#02</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to determine a set of tasks for the PHR Account Holder based on a previously-defined set of business rules.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.3.5.2#03</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to capture, maintain, and render an indication of the status of tasks (e.g., completed or performed). For example, the dressing for a laceration needs to be changed every three days, but the PHR Account Holder failed to note yesterday that the dressing was successfully changed as required. Another example is the requirement to post an indication to the PHR system regarding daily compliance with dietary guidelines.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.3.5.2#04</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <i>dependent</i>\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to render tasks in a sorted manner (e.g., by status or priority) according to user-preference, organizational policy, and/or jurisdictional law.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.3.5.2#05</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD present each task with a brief description and date on a task list included on the PHR Account Holder's summary view or dashboard.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.3.5.2#06</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability for the PHR Account Holder to capture, maintain, and render descriptions of health-related tasks (and associated dates/times for those tasks).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.3.5.2#07</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to capture, maintain, and render communications that were received from others who are performing tasks (e.g., an indication from a member of a care team who completed or performed a certain task).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.3.5.2#08</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD conform to TI.7 (Workflow Management) to manage workflows and tasks that involve communications with others.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n </table>\n</div>"
},
"extension" : [
{
"url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
"valueCode" : "ehr"
}
],
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/Requirements/PHRSFMR2-PH.3.5.2",
"version" : "2.0.1-ballot",
"name" : "PH_3_5_2_Manage_Tasks",
"title" : "PH.3.5.2 Manage Tasks (Function)",
"status" : "active",
"date" : "2025-04-03T15:15:30+00:00",
"publisher" : "EHR WG",
"contact" : [
{
"telecom" : [
{
"system" : "url",
"value" : "http://www.hl7.org/Special/committees/ehr"
}
]
}
],
"description" : "Healthcare events or activities that require the PHR Account Holder's participation can be organized as tasks.",
"purpose" : "Care plans and other health care activities can be broken down into specific steps or tasks and organized on a task list that may be sorted by priority, date and time, problem, provider, and so forth. The task list entries should serve as an index to their supporting documents.\r\n\r\nExample(s): Directions for a dressing change at a specific time of day can be displayed as an entry on the task list.",
"statement" : [
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.3.5.2-01",
"label" : "PH.3.5.2#01",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability for the PHR Account Holder to manage self-care, health maintenance, preventive, and wellness tasks, including the management of task status (e.g., performed, rescheduled, or canceled).",
"satisfiedBy" : [
"https://www.hl7.org/fhir/task.html"
]
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.3.5.2-02",
"label" : "PH.3.5.2#02",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to determine a set of tasks for the PHR Account Holder based on a previously-defined set of business rules."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.3.5.2-03",
"label" : "PH.3.5.2#03",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to capture, maintain, and render an indication of the status of tasks (e.g., completed or performed). For example, the dressing for a laceration needs to be changed every three days, but the PHR Account Holder failed to note yesterday that the dressing was successfully changed as required. Another example is the requirement to post an indication to the PHR system regarding daily compliance with dietary guidelines."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : true
}
],
"key" : "PHRSFMR2-PH.3.5.2-04",
"label" : "PH.3.5.2#04",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to render tasks in a sorted manner (e.g., by status or priority) according to user-preference, organizational policy, and/or jurisdictional law."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.3.5.2-05",
"label" : "PH.3.5.2#05",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD present each task with a brief description and date on a task list included on the PHR Account Holder's summary view or dashboard."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.3.5.2-06",
"label" : "PH.3.5.2#06",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability for the PHR Account Holder to capture, maintain, and render descriptions of health-related tasks (and associated dates/times for those tasks)."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.3.5.2-07",
"label" : "PH.3.5.2#07",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to capture, maintain, and render communications that were received from others who are performing tasks (e.g., an indication from a member of a care team who completed or performed a certain task)."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.3.5.2-08",
"label" : "PH.3.5.2#08",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD conform to TI.7 (Workflow Management) to manage workflows and tasks that involve communications with others."
}
]
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.